home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: alt.winsock.trumpet,alt.winsock,comp.dcom.modems
- Path: news.csra.net!not-for-mail
- From: jimwhite@cent.com (Jim White)
- Subject: Re: Comm Overrun Errors - A Possible Solution
- Message-ID: <313ae717.308903277@news.csra.net>
- Date: Mon, 04 Mar 1996 12:55:08 GMT
- Organization: South Shore Software
- Reply-To: jimwhite@cent.com
- References: <4emn1a$5ba@trojan.neta.com> <4esm85$qd2@fountain.mindlink.net> <4f03sk$o7g@zoom2.telepath.com> <31169d53.12139962@news.gnn.com> <3122446E.5898@dircon.co.uk> <3122928A.4E3A@cerberus-sys.com> <troy-0103961527260001@denim.csn.net> <3137B792.3B0A@cerberus-sys.com> <31394fb3.5124008@news.iapc.net>
- X-Newsreader: Forte Agent .99d/32.168
-
- dyn88olds@iapc.net ("Dynamic 88 Olds, Where The Action Is In 1964")
- wrote:
-
- >Put this message in the 386Enh section of your System.ini:
- >
- >Com(?)FIFO=1
- >
- >In all the MS literature the figure is misprinted as Com(whatever your
- >modem is on}=on
- >
- >Check it out. This should help alot.
- >
- >howard Rubin
- >
-
- in the various windows ini files, there are several alliases for a
- variety of "boolean" type variables... 1=on=yes=true, 0=off=no=false,
- etc. .....
-
- ==========>
- Jim White
- South Shore Software
- jimwhite@cent.com
- www.cent.com/paradise.net
- jimwhite@msn.com
-
-